home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
rbbs_pc
/
msgtos13.zip
/
MSGTOSS.CFG
< prev
next >
Wrap
Text File
|
1990-03-31
|
21KB
|
412 lines
; You can remove the commented lines (after the NODE parameters) for faster
; initialization, but do NOT remove any of the "--->" lines. MSGTOSS expects
; them to all be there. The ONLY parameters safe to comment out are the
; UTIL1, UTIL2 & UNARCH parameters!
;
FILES------->C:\MAIL\FILES\
WORKDIR----->M:\
LOGDIR------>C:\BT\
MESSAGES---->C:\RBBS\MESSAGES
RBBS-MAX---->999
ELASTIC----->NO
MARGIN------>72
SECL-------->SEEN-BY:
SECL-------->
DUPFILE----->MSGTOSS.EID
MAXAREAS---->100
DUPSIZE----->100
UNARCH------>SPAZ -F -Q C:\MAIL\FILES C:\BT\
CONFWAIT---->10
CONFLOCK---->ALLFIG C:\RBBS\ALL1 130 N J 100 \n
PKTWILD----->*.PKT *.?UT
PURGECMD---->MU-PURGE [MSGFILE] /MSG:PIP
RENUMCMD---->MSGRENUM /MSG:[MSGFILE] /USR:[USRFILE] /DDA /NET /FIX
MAILWCMD---->MAILWAIT /MSG:[MSGFILE] /USR:[USRFILE] /DDA /NET /NAM:MIKE ZAKHAROFF /SYS:100 /FIX /LOG
BLANKMSG---->C:\RBBS\BLANKM.DEF
FIXMSGCMD--->FIXMSG [MSGFILE] /NET
RENUMBAT---->MSGCLEAN.BAT
MAILWBAT---->MSGCLEAN.BAT
;UTIL1------->MSGCLEAN.BAT
;UTIL1CMD---->SUBJECT I:[MSGFILE] O:[WELFILE] C:[AREA] L:15 S:
;UTIL2------->
;UTIL2CMD---->
ECHOSEC----->40
PRIVATE----->NO
KILLOVER---->3500
MAINT%LO---->80
MAINT%HI---->89
DAYSTOSYS--->60
DAYSFRSYS--->60
DELREADSYS-->NO
DAYSTOUSR--->60
DAYSFRUSR--->60
DELREADUSR-->NO
YEAR-------->1989
SYSALIAS---->SUPER TOSSER
SYSNAME----->!MIKE ZAKHAROFF
SYSNAME----->=SYSOP
NODE-------->1:343/36
NODE-------->8:918/1
;
; FILES - Directory INCOMING mail and files go to FIRST
;
; WORKDIR - RAM Disk (recommended) where MSGTOSS will COPY the current
; message base being PURGED or SIZED. In addition, if
; PAGING to disk is necessary (if a conference has over
; 2000 users) MSGTOSS will write the excess users to the RAM
; disk for faster operation. Will check for available space
; first. Not enough space will cause default directory to
; be used. Need to specify the "/WDIR" switch to activate.
;
; NOTE: Does NOT have to be a RAM disk. If for example you
; ran out of disk space, you can SIZE the message
; bases via a WORKDIR that has plenty of space. In
; addition, the use of the WORKDIR provides an extra
; safety margin while MSGTOSS is purging a message
; base, as if power is lost while purging, lost chains
; may be present in the message base. However, if
; using the /FIX switch, MSGTOSS will detect the
; corruption and fix the message base anyway (using
; FIXMSG).
;
; LOGDIR - Where MSGTOSS will write its MSGTOSS.LOG, MSGTOSS.ERR
; & MSGTOSS.DUP files. Needs to end with a trailing
; backslash. Blank will end up in default directory.
;
; MESSAGES - Path/FileName of Main RBBS Message Base. This is used
; while using the /WAIT switches, as MSGTOSS will monitor
; the NODE records of the main RBBS message base to see
; whether all users are of-line.
;
; RBBS-MAX - Reflects the "current" RBBS-PC maximum messages. The
; maximum of 999 may soon change to 9999, so this is
; why the "RBBS-MAX---->" parameter is present in the
; MSGTOSS.CFG file. The default entry is 999, which
; reflects the "current" RBBS-PC maximum. In the event the
; maximum is raised (future releases of RBBS-PC) the MSGTOSS
; "RBBS-MAX--->" parameter will have to be adjusted.
;
; ELASTIC - Either "YES" or "NO". This is designed to support the new
; "elastic message bases" of RBBS-PC. What this actually
; does is tell MSGTOSS to make the "maximum messages" value
; that is present in the message base "checkpoint record" to
; be the value of the "RBBS-MAX--->" parameter, no matter
; what MSGTOSS calculates it to be normally.
;
; NOTE: For proper operation of the ELASTIC message bases,
; the MAINT%LO and MAINT%HI parameters should be set
; to a value of 100 each. This tells MSGTOSS during
; purging, sizing and tossing to leave as little
; amount of slack space at the end of the message
; bases as possible (100 percent full at all times).
; RBBS will expand the message bases as users enter
; new messages. In addition, RBBSMAIL will cut off
; any slack present in the message base during a scan
; mode (when set for ELASTIC operation).
;
;
; NOTE: You can still use the "/PREP" switch, even though
; you set ELASTIC to "YES". MSGTOSS will still CHOP
; the message bases back down to the "|Rxxxx|" values
; set in the MSGTOSS.BBS file.
;
; MARGIN - What right margin should the RBBS conferences should be
; set to. RBBS normally formats newly entered messages to
; 72. It should ne noted that setting the right margin
; beyond the RBBS expected value of 72 may cause editing to
; be more difficult, but will make the messages more
; pleasing to read. Values beyond 77 are not recommended.
; A value of 39 can be used to format the message bases to
; support 40 column users.
;
; The "/MRGN:xx" command line switch overrides the MARGIN
; parameter.
;
; SECL - These are utilized ONLY when the "/SECL" switch is
; activated (which also requires the "/FMAS" switch). These
; entries determine exactly what lines in the RBBS echomail
; messages (not FIDO) are to be ignored during tossing.
;
; Example: You want to strip all occurances off the
; "SEEN-BY:" lines in RBBS messages:
;
; SECL-------->SEEN-BY:
;
; Example: Most echomail control lines begin with a "" so:
;
; SECL-------->
;
; Will strip EID:, PATH:, MSGID: & VIA: and any other
; line that begins with an .
;
; Example: You ONLY want to strip PATH: and VIA: lines:
;
; SECL-------->PATH:
; SECL-------->VIA:
;
; All other lines that begin with an will be imported as
; normal.
;
; NOTE: The most restrictive entry will override a similar
; less restrictive entry, example:
;
; SECL-------->
; SECL-------->PATH:
;
; The first entry ALREADY will strip the second entry!
;
; NOTE: Up to 20 "SECL-------->" entries are possible.
;
; DUPFILE - Created by MSGTOSS, Database of EID codes. Use the /WDIR
; (work directory) switch for automatic copying to/from ram
; disk for faster dup checking.
;
; MAXAREAS - Reserves so many spaces in the EID database. Max number
; of conferences you would EVER have (I have 28, and mine is
; set for 100, which I would never carry). Each require 26
; bytes.
;
; DUPSIZE - The number of previous messages to keep track of in each
; area of each conference. Basically, the bigger, the
; slower messsage processing. If your message bases average
; 100 messages, then set to at least 75. However, numbers
; over 500-1000 are possible, but standby for some SLOW
; tossing and a LARGE MSGTOSS.EID file! For optimum
; processing its best to use the /WDIR (work directory)
; switch to automatically place MSGTOSS.EID in a RAMDISK
; for faster processing. MSGTOSS will automatically copy
; the database back after tossing is complete.
;
; NOTE: If you have a reliable HUB, who faithfully checks
; for DUPS before sending to you, then the use of the /CDUP
; switch may NOT be necessary and will make mail events as
; fast as possible.
;
; WARNING!: These TWO parameters (DUPSIZE and MAXAREAS) are
; 'one-time-shot' parameters. You can ONLY change these
; parameters by first erasing the MSGTOSS.EID database, and
; re-executing MSGTOSS, which will then format a *new*
; MSGTOSS.EID file. In addition, these TWO parameters can
; drastically slow down tossing after they get filled up
; with EID: codes. So if you decide to make these 10000
; each, tossing may take forever.
;
; NOTE: Executing with the /CDUP switch the first time will
; create MSGTOSS.EID. Depending on the values of
; MAXAREAS and DUPSIZE (mostly) the size of the EID
; database file will vary considerably. The ap-
; proximate size of the EID database file can be esti-
; mated using the following formula:
;
; ((13 * DUPSIZE) * NUMBER.OF.AREAS.YOU.HAVE)) + (MAXAREAS * 26)
;
; UNARCH - Command to issue to unarchive mail packets. Recommended
; to use only SPAZ.COM, because it can handle ZIP, LHARC,
; ARC etc.
;
; SPAZ -F -Q C:\MAIL\FILES C:\BT\
; ------------- ----------------------------
; Incoming Mail Where PKTS go for processing
;
; NOTE!! --> Where trailing back-slashes are!
;
; NOTE: MSGTOSS looks in either the default directory (where
; you executed MSGTOSS), and the directory specified
; bythe FILES---> parameter for PKTs. Therefore, the
; "C:\BT\" as shown above is also where MSGTOSS.CFG,
; MSGTOSS.BBS and other control files are (like
; RBBSMAIL.CFG). However, you can set the above
; quoted directory to be ANY drive/directory, but you
; MUST make sure you first change drive/directories
; in your batch file, and execute MSGTOSS via the
; /CFG: and /BBS: switches, to tell MSGTOSS where
; its control files are.
;
; NOTE: If you set the UNARCH parameter to blank, then
; MSGTOSS will NOT shell out internally. If you are
; having a memory problem, then you can simply execute
; SPAZ in your batch file before executing MSGTOSS.
;
; CONFWAIT - Number of minutes to wait till users are off line (used
; with the /WAIT or /WAIT-F switches)
;
; CONFLOCK - Command to place in MSGWAIT.BAT file created to lock
; conferences (used with /WAIT options)
;
; PKTWILD - Wildcards of what extentions FIDO Packets can be
;
; PURGECMD - Will purge [MSGFILE] with What you put here
;
; NOTE: This is ONLY used in conjunction with the /PEXT
; switch. MSGTOSS by DEFAULT purges the message
; bases INTERNALLY, thus this is ONLY provided for
; those few who have a special need and desire to use
; MU-PURGE vice MSGTOSS's internal purging!
;
; NOTE: MSGTOSS supports dynamic USER File replacement
; parameter for this switch. To use this, place
; [USERFILE] within the command line.
;
; IE: MU-PURGE [MSGFILE] /MSG: LOG PIP // ([USRFILE])
;
;
; RENUMCMD - Re-number [MSGFILE] using [USRFILE] with what you put here
;
; MAILWCMD - Set Mailwaiting bit [MSGFILE] [USRFILE] with what you put
; here, using dynamic replacement parameters.
;
; NOTE: This command line requires the /MEXT switch to be on
; the command line, otherwise MSGTOSS will DEFAULT to
; its INTERNAL Mailwaiting code. Use this ONLY if you
; require the special features of MAILWAIT.
;
; FIXMSGCMD - Fix [MSGFILE] with this ([USRFILE] available)
;
; RENUMBAT - File created by MSGTOSS which contains RENUMCMD
;
; MAILWBAT - File created by MSGTOSS which contains MAILWCMD
;
; BLANKMSG - A "model" messsage base (un-corrupt, small) that will be
; used with the "/FIXC" command line. If FIXMSG fails twice
; then the message base entered here will be copied over the
; original (corrupt) message base. The corrupt message base
; will be renamed *.BAD.
;
; UTIL1 - Batch file or ?? which contains UTIL1CMD commands
;
; UTIL1CMD - Miscellaneous utility command [MSGFILE], [USRFILE], [AREA]
; & [WELFILE] available for processing.
;
; UTIL2 - Batch file or ?? which contains UTIL2CMD commands
;
; UTIL2CMD - Miscellaneous utility command [MSGFILE], [USRFILE], [AREA]
; & [WELFILE] available for processing.
;
; ECHOSEC - Minimum Security level you allow for conference Access.
; This is used to set the security level of the message dur-
; ing tossing, and during purging as users with the security
; level of ECHOSEC or higher will not have their messages
; deleted.
;
; NOTE: This is the security level (applicable conference
; user file) whose members messages will NOT BE KILLED
; unless they were already KILLED.
;
; NOTE: This will be OVERRIDDEN by the DAYSTOUSR, DAYSFRUSR
; or the DELREADUSR parameters.
;
; PRIVATE - Either YES or NO. Whether to honor incoming PRIVATE echo
; mail. Normally set to NO, which converts to public.
; Setting to YES will slow down tossing. If tossing NETMAIL
; into an RBBS conference then MSGTOSS will
; AUTOMATICALLY check it the message is private. Better to
; set this switch to NO.
;
; KILLOVER - Prevent TOSSING (ignore) of any message over this size
;
; MAINT%LO - When a purge is required, what % capacity to purge to.
;
; MAINT%HI - What is the MAXIMUM % capacity before a purge is required.
;
; NOTE: These two parameters control the purging activity of
; MSGTOSS. MSGTOSS will automatically maintain the
; percent capacity of all messages bases somewhere BE-
; TWEEN these two values. Make sure MAINT%HI is a
; larger value of MAINT%LO (or equal), and that they
; do not exceed a value of 100 each.
;
; DAYSTOSYS - Applies ONLY to messages TO the SYSOP: How many days old
; the message is before it will be KILLED automatically.
;
; DAYSFRSYS - Applies ONLY to messages FROM the SYSOP: How many days old
; the message is before it will be KILLED automatically
;
; DELREADSYS - Applies ONLY to messages TO the SYSOP: If the message has
; been read by the SYSOP, then automatically KILL it,
; regardless of the setting of DAYSTOSYS parameter. If
; unread, will remain until the DAYSTOSYS parameter applies.
; (YES or NO).
;
; DAYSTOUSR - Applies ONLY to messages TO the USERS: How many days old
; the message is before it will be KILLED automatically.
;
; DAYSFRUSR - Applies ONLY to messages FROM the USERS: How many days old
; the message is before it will be KILLED automatically
;
; DELREADUSR - Applies ONLY to messages TO the USERS: If the message has
; been read by the USER, then automatically KILL it,
; regardless of the setting of DAYSTOUSRS parameter. If
; unread, will remain until the DAYSTOUSR parameter applies.
; (YES or NO).
;
; YEAR - MSGTOSS depends on the SYSTEM CLOCK. If for some reason
; the system clock YEAR does NOT match the YEAR Parameter,
; MSGTOSS will abort. This is to help prevent the
; accidental deletion of messages based on the
; DAYSTO/DAYSFR Parameters by a faulty system clock.
;
; NOTE: Reset this parameter on New Years Day!
;
; SYSALIAS - The SYSALIAS parameter tells MSGTOSS which user name is
; considered the SYSOP. This should be the same name as was
; entered in CONFIG for the secret remote logon, and for
; LOCAL logon (ESC switch). Any messages that match those
; as specified by the various SYSNAME(s) will cause the
; mailwaiting bit for the SYSALIAS user to be set, and cause
; the TO: field to be changed to the text 'SYSOP', if
; 'SYSOP' is not already part of the TO: field.
;
; SYSNAME - This parameter controls what messages are considered the
; SYSOP. This is used during the PURGING and MAILWAITING
; phases of the MSGTOSS. MSGTOSS will set the SYSOP's
; mailwaiting bit ONLY if the message matches the below
; criteria, and will be exempt from purging as well until
; killed.
;
; The FIRST CHARACTER must be either a '!' or a '=', nothing
; else is allowed. The '!' means CONTAINS and the '=' means
; EXACT.
;
; !SYSOP keep messages that contain the string 'SYSOP' (Not
; recommended, as every message to 'JOE SYSOP' will set the
; mailwaiting bit for the SYSALIAS user (sysop).
;
; =SYSOP will match on messages that ONLY have 'SYSOP' in
; TO/FROM, will set the mailwaiting bits, and be exempt from
; purging until either killed by the sysop, or DAYS(s)
; parameters apply.
;
; !YOUR REALNAME incase a message 'MIKE ZAKHAROFF @1:343/36'
; !SYSOP @343/36 is also recommended or just '!SYSOP @'
;
; NOTE: During the MAILWAITING processing, MSGTOSS will
; convert messages addressed to your SYSNAMES to
; 'SYSOP', if SYSOP is not already part of the 'TO:'
; name, and set the mailwaiting bit for the user you
; entered under the SYSALIAS parameter.
;
; Example:A message arrives to 'MIKE ZAKHAROFF'.
; Because a SYSNAME is '!MIKE ZAKHAROFF' that message
; will be converted to 'SYSOP' in the TO: Field.
;
; Example:A message arrives to 'JOE SYSOP' and
; '=SYSOP' is only entered as a SYSNAME. That message
; will be treated as if it is another junk message,
; and MSGTOSS will purge it whenever it thinks it need
; to and will NOT set the sysops mailwaiting bit.
;
; NOTE: ANY message addressed to your SYSNAMES(s) will
; cause the mailwaiting bit to be set for the user as
; specified by your SYSALIAS!
;
; NOTE: You can have up to 10 SYSNAME(s)
;
; NODE - Full NET/NODE of all your FidoNet compatible AKA's
; (1:343/36)
;
; NOTE: You can have up to 10 NET/NODES
;
; NOTE: Place the net/node that gets the most traffic FIRST,
; as they are checked sequentially.